docs(skills): modularize governance references - #670
Open
beruro wants to merge 1 commit into
Open
Conversation
beruro
force-pushed
the
junyu/skill-governance-modularization
branch
from
August 4, 2026 05:26
62dd0f2 to
ab9abb5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Several workspace skills keep their full methodology, examples, failure histories, commands, and delivery rules in one large
SKILL.md. Agents must load all of that material even when only one phase is relevant, while the long files make routing rules harder to review and maintain.Solution
Turn each main
SKILL.mdinto a concise router and move detailed guidance into namedreferences/files for architecture audit, dual-instance verification, E2E testing, performance guard, and React best practices. Update.gitignoreso the newly vendored architecture and E2E references are tracked. During integration with currentdevelop, preserve the newly strengthened dual-instance fleet invariants and add a mandatory determinism reference covering two-boot comparison, liveness, fault injection, unexplained deltas, and baseline attribution.Potential risks
Moving methodology text can accidentally omit a rule or leave a broken relative link, which would make an agent skip required evidence. The change preserves the main routing contracts, validates every referenced file, and explicitly reconciles the latest dual-instance additions rather than replacing them with the older modularized text. No runtime code, dependencies, persisted data, or public API changes are involved. Rollback is a documentation-only revert.
Verification
nameanddescription— passed.references/...link under.orgii/skillsand verified its target exists — passed.git diff --cached --check— passed.origin/develop; only.gitignoreand the five skill packages are included.dual-instance-verificationconflict with currentdevelop, retaining fleet-wide epoch/count invariants, destructive-effect auditing, resource anomaly handling, and mandatory determinism/fault-injection guidance.No product tests or UI screenshots were run because this PR changes agent methodology Markdown and ignore rules only.